-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Production OTA: Add link for offline keys (requirement) and reason for motivation to do static deltas #610
Conversation
Docs for 464ddee are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2386/docs/artifacts/html/index.html |
Docs for 34969c0 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2387/docs/artifacts/html/index.html |
34969c0
to
7bd0383
Compare
Docs for 7bd0383 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2388/docs/artifacts/html/index.html |
Docs for c7d7727 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2389/docs/artifacts/html/index.html |
c7d7727
to
5b85a90
Compare
Docs for 5b85a90 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2390/docs/artifacts/html/index.html |
5b85a90
to
6c433e1
Compare
Docs for 6c433e1 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2391/docs/artifacts/html/index.html |
6c433e1
to
035fd34
Compare
Docs for 035fd34 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2392/docs/artifacts/html/index.html |
035fd34
to
f58974e
Compare
Docs for f58974e are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2393/docs/artifacts/html/index.html |
499ad8f
to
f2ce3da
Compare
Docs for 499ad8f are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2394/docs/artifacts/html/index.html |
Docs for f2ce3da are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2395/docs/artifacts/html/index.html |
IMO, I would let customer support team representatives to judge about the given doc/TUF clarification. Personally, as for me, it's really hard to assess objectively this document explanation in terms of helping customers to grok the TUF stuff. The key reason, I've working with TUF many years and know our TUF related implementation from inside. @caiotpereira @vanmaegima Please, look into this doc and provide your feedback. |
e5dfd30
to
7f605f4
Compare
This comment was marked as resolved.
This comment was marked as resolved.
7f605f4
to
1eeba94
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only few minor suggestions, please ignore then if you think they don't fit!
f7e5e19
to
5e3313c
Compare
…e necessity of obtaining the targets key, a prerequisite to proceed. Signed-off-by: Camila Macedo <[email protected]> Co-authored-by: vkhoroz <[email protected]>
49be886
to
6a18561
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with the current version.
@kprosise needs to approve.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this PR, I've mainly let the text suggested by @vkhoroz , which seems to be appropriate. I believe this is the best approach. We can discuss other changes or additions in follow-up PRs.Sorry for any inconvenience or disturbance I may have caused.
Thank you for your attention and time
I hope it small nit changes are good to fly,
Please, let me know if any further changes would be required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple small changes suggested
Signed-off-by: Camila Macedo <[email protected]> Co-authored-by: Katrina Prosise <[email protected]>
fefc089
to
2bcd40e
Compare
Signed-off-by: Camila Macedo [email protected]
Readiness
Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."
make linkcheck
.-s, --signoff
).-S, --gpg-sign
).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.